Since collision data is always defined with, and associated with maps,
it makes sense to store the collision data INSIDE the map movieClip
in a standard form.


There are many good reasons to do this:
- Collision data takes a standard form.
	(other systems can use it)
- Collision is easily implemented.
	(it comes with the map)
- twoPointCollide() can be included.
	(makes it easy for any sprite to do collision)


The map can still be utilized as a dumb display.
Simply ignore the collision system.

I recommend encapsulating the collision system inside the map system
as an object:
	map_mc.collision_obj

I recommend adding twoPointCollision() to this collision system.
	(it doesn't need to be included seperately)

The map's load functions also load the collision data.
